
╔═════════╦════════════════════════════════════════════════════════════
║ GT-HELP ║ Additional Routing Files (see also ROUTING.HLP)
╚═════════╩════════════════════════════════════════════════════════════

    Since all the Netmail programs support the /R:xxxxxx switch, you can
    have as many routing files as is necessary.

    Additional routing files can have any name you choose.  However, if you
    wish to be able to edit them with GT-HELP you will need to use the .RTG
    suffix.


┌────────────────────────────────────────┐
│ Do I need an additional routing file ? │
└────────────────────────────────────────┘

    Probably not, if you put all your mail through a single hub and have no
    unusual requirements.  But unless you live in the USA, you are unlikely
    be able to send .DX messages or place outgoing crash calls to overseas
    destinations without at least one additional routing file.  This is
    necessary because a single routing file can support only 2 types of
    dial prefix.

    As an example, a UK node might have :

        Area (defined in schedule.bbs)      44

        Prefixes        (+)     0       for UK numbers
                        ($)     0101    for USA
                        (*)     010     for rest of world

        Routing.BBS     using   prefixes Local (+) Distant (*) inbound
                                all USA nodes

        USA.RTG         using   prefixes Local (+) Distant ($) inbound
                                all Rest of World nodes

    The format of the additional routing is exactly as the standard
    routing.bbs.  But you may find it convenient to separate sections which
    are common to more than one routing file, and to "include" them by
    reference.  For example :

        $DISTRIB.INC

    could be included in all routing files in place of the message
    distribution to specify that the distribution information is contained
    in a file with that name, rather than having to repeat the same
    information in each routing file.

